I recently setup code coverage with Golang and hit a snag in how our coverage reports were generating. Turns out, it was related to the module name we used. Since it didn't match the directory structure of our project, the file in our repository wasn't being found and resulting in the following error:

info [ReportRules] Parsing coverage data from: /my/coverage/file.out ...  - (ReportRules.scala:41)
info [ReportRules] Coverage parser used is com.codacy.parsers.implementation.GoParser$@1f392a2f  - (ReportRules.scala:46)
warn [GitFileNameUpdaterAndFilter] File: Ignoring mymodule/XX.go for coverage calculation. No matching file found in the repository.  - (GitFileNameUpdaterAndFilter.scala:24)
error [CodacyCoverageReporter] No coverage data was sent  - (CodacyCoverageReporter.scala:28)

Note: I changed some of the details but the directory structure is my-module/go.mod

👀 Live preview

http://127.0.0.1:8000/coverage-reporter/uploading-coverage-in-advanced-scenarios/#golang

🚧 To do

• If relevant, include the Jira issue key at the end of the pull request title
• Perform a self-review of the changes
• Fix any issues reported by the CI/CD